翻訳と辞書
Words near each other
・ Enterprise Lake
・ Enterprise legal management
・ Enterprise liability
・ Enterprise Library
・ Enterprise life cycle
・ Enterprise liquidity
・ Enterprise Lithuania
・ Enterprise Mag
・ Enterprise Magazine
・ Enterprise manufacturing intelligence
・ Enterprise marketing management
・ Enterprise Mashup Markup Language
・ Enterprise master patient index
・ Enterprise Media Bean
・ Enterprise Mercantile and Milling Company Building
Enterprise messaging system
・ Enterprise Mill
・ Enterprise Mobile Application
・ Enterprise mobility management
・ Enterprise modelling
・ Enterprise Municipal Airport
・ Enterprise Municipal Airport (Alabama)
・ Enterprise Municipal Airport (Oregon)
・ Enterprise Objects Framework
・ Enterprise of Ulster
・ Enterprise Oil
・ Enterprise output management
・ Enterprise performance management
・ Enterprise Planing Mill
・ Enterprise planning system


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Enterprise messaging system : ウィキペディア英語版
Enterprise messaging system

An enterprise messaging system (EMS) is a set of published enterprise-wide standards that allows organizations to send semantically precise messages between computer systems. EMS systems promote loosely coupled architectures that allow changes in the formats of messages to have minimum impact on message subscribers. EMS systems are facilitated by the use of structured messages (such as using XML or JSON), and appropriate protocols, such as DDS, MSMQ, AMQP or SOAP with web services.
EMS usually takes into account the following considerations:
# ''Security'': Messages must be encrypted if they travel over public interfaces. Messages must be authenticated or digitally signed if the receiver is to have confidence that the messages have not been tampered with in transit.
# ''Routing'': Messages need to be routed efficiently from the sender to the receiver. Intermediate nodes may need to route the messages if the body of the message is encrypted.
# ''Metadata'': The body of the document contains information that must be unambiguously interpreted. Metadata registries should be used to create precise definitions for each data element.
# ''Subscription'': Systems should be able to subscribe to all messages that match a specific pattern. Messages with a specific content may be routed differently. For example some messages may have different priority or security policies.
# ''Policy'': Enterprise messaging systems should provide some consideration for a centralized policy of messages such as what classes or roles of users can access different fields of any message.
==Separation of message header and message body==
The design of an EMS is usually broken down into two sections:
# ''Message header design'' – Message headers contain the information necessary to route messages. Message headers are usually coded in clear text so that intermediate nodes receive all the necessary information they need to route and prioritize the message. Message headers are analogous to the information printed on the outside of a letter (to, from, priority of message etc.)
# ''Message body semantics'' – Message body semantics include the precise definition of all of the data elements in the body of the message. Message semantics can be aided by the use of a precise data dictionary that documents metadata.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Enterprise messaging system」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.